fix: use plugin-qualified MCP tool names in hooks - #179
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe hook commands now accept plugin names and generate Claude MCP references with the plugin namespace. Session-start directives and pre-tool-use suggestions use the shared reference builder. Tests cover plugin-qualified, standalone, Cursor, and JSON hook output. ChangesPlugin-aware hook processing
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant HookCommand
participant MCPReferenceBuilder
participant ClaudeCodeMCP
HookCommand->>MCPReferenceBuilder: Build reference with plugin name
MCPReferenceBuilder-->>HookCommand: Return plugin-qualified semantic_search reference
HookCommand->>ClaudeCodeMCP: Emit directive or pre-tool-use suggestion
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
jonas-jonas
left a comment
There was a problem hiding this comment.
Also an into this, seems like it's a good fix
failures seem unrelated?
Fixes Claude Code plugin hook guidance to reference plugin-qualified semantic search MCP tool names and tells agents to load deferred tools before calling them.
Adds an optional --plugin-name flag so standalone CLI and Cursor behavior remain unchanged while bundled hooks pass lumen.
Extends hook tests to cover plugin-qualified and legacy tool references.
Closes #176.
Summary by CodeRabbit
New Features
Bug Fixes